I'm going to update Atom's update-atom-shell-task.coffee to download atom-shell with the Releases API, but since atom-shell is private authentication would be required, should the script ask the user for a token or just has one hard-coded? /cc @kevinsawicki

@zcbenz Not sure what the right answer is, let me look into what our options are first.

When I looked into this last time I used the cli keychain commands (for OS
X). You can grab the users github token from those and it will prompt the
user for access to the keychain.

I can get you more info tomorrow if you need it.

On Thursday, September 26, 2013, Kevin Sawicki wrote:

@zcbenz https://github.com/zcbenz Not sure what the right answer is,
let me look into what our options are first.

—
Reply to this email directly or view it on GitHubhttps://github.com//pull/103#issuecomment-25217110
.

@probablycorey did that work on CI?

Ugh, nope. I don't think that will work with CI.

On Thursday, September 26, 2013, Kevin Sawicki wrote:

@probablycorey https://github.com/probablycorey did that work on CI?

—
Reply to this email directly or view it on GitHubhttps://github.com//pull/103#issuecomment-25217366
.

We could use a combo of an env var + cli keychain. That way we don't check
in a token, CI will work and humans can use their keychain.

On Thursday, September 26, 2013, Corey Johnson wrote:

Ugh, nope. I don't think that will work with CI.

On Thursday, September 26, 2013, Kevin Sawicki wrote:

@probablycorey https://github.com/probablycorey did that work on CI?

—
Reply to this email directly or view it on GitHubhttps://github.com//pull/103#issuecomment-25217366
.

@probablycorey I opened a PR for this: atom/atom#890, it would be great if you can help finish the keychain and CI parts.